System and Method for Providing Diverse Secure Data Communication Permissions to Trusted Applications on a Portable Communication Device

ABSTRACT

A system for providing first and second trusted applications diverse permission to communicate via a secure element. The system comprising first digital identifier and digital token operably associated with the first trusted application; a second digital identifier and digital token operably associated with the second trusted application. The system further includes a card services module that provides an application programming interface to the secure element supported by a secure data table including first and second sets of permissions. The card services module issues one or more commands to the secure element based on a first action requested by the first trusted application in conjunction with the presentation of the first digital token only if the one or more commands will not violate the first set of permissions. A method is also disclosed.

This application claims priority from U.S. Provisional PatentApplication No. 61/414,847, filed on Nov. 17, 2010, entitled “System andMethod for Providing Secure Data Communication Functionality to aVariety of Applications on a Portable Communication Device.”

TECHNICAL FIELD

The present invention relates generally to the use of secure data tocomplete a wireless transaction, and more particularly to a system andmethod for providing diverse secure data communication functionality toa plurality of trusted applications on a portable communication device.

BACKGROUND

Wireless transactions using RFID-based proximity cards are fairly commonplace. For instance, many workers use RFID keycards to gain access totheir workplace and drivers use RFID passes to pay tolls at highwayspeeds. RFID, which stands for radio-frequency identification, useselectromagnetic waves to exchange data between a terminal and someobject for the purpose of identification. More recently, companies havebeen trying to use RFIDs to supported by cellular telephones toimplement an electronic payment product (i.e. credit and/or debit card).However, basic RFID technology raises a number of security concerns thathave prompted modifications of the basic technology. Still, widespreadadoption of RFID as a mechanism for electronic payments has been slow.

Near Field Communication (NFC) is another technology that useselectromagnetic waves to exchange data. NFC waves are only transmittedover a short-range (on the order of a few inches) and athigh-frequencies. NFC devices are already being used to make payments atpoint of sale devices. NFC is an open standard (see, e.g. ISO/IEC 18092)specifying modulation schemes, coding, transfer speeds and RF interface.There has been wider adoption of NFC as a communication platform becauseit provides better security for financial transactions and accesscontrol. Other short distance communication protocols are known and maygain acceptance for use in supporting financial transactions and accesscontrol.

Many applications have been developed for use in association withportable communications devices. Some of these applications wouldbenefit from having access to electronic funds to facilitate theconsumer's consummation of a electronic transactions via thoseapplications, such as the purchase of goods over the Internet. Stillother applications have no purpose if they cannot access the secure datasubsystem of the portable communication device.

Card issuers are interested in facilitating the option to pay forapplication usage and ecommerce using their credit/debit card products.Notwithstanding their self-interest in enabling third party applicationsto access their financial products, the card issuers may have serioussecurity concerns about broad distribution of security protocols.Similarly, the third party developers may not be interested indeveloping financial product subroutines. Accordingly, there is a needin the industry for an electronic wallet that is accessible by thirdparty programs to facilitate the payment of charges associated with theuse of those programs. The application accessible electronic wallet mayalso be used via direct access by the consumer to the mobileapplication.

Accordingly, the present invention seeks to provide one or moresolutions to the foregoing problems and related problems as would beunderstood by those of ordinary skill in the art having the presentspecification before them. These and other objects and advantages of thepresent disclosure will be apparent to those of ordinary skill in theart having the present drawings, specifications, and claims before them.It is intended that all such additional systems, methods, features, andadvantages be included within this description, be within the scope ofthe disclosure, and be protected by the accompanying claims.

SUMMARY OF THE INVENTION

The present invention relates to a system for providing first and secondtrusted applications diverse permission to communicate via a secureelement associated with a portable communication device. The systemcomprises a first digital identifier and a first digital token operablyassociated with the first trusted application; a second digitalidentifier and a second digital token operably associated with thesecond trusted application; a card services module disposed on theportable communication device to provide an application programminginterface; and a secure data table electronically associated with thecard service module, the secure data table including a first entrypairing the first digital identifier with the first digital token and asecond entry pairing the second digital identifier with the seconddigital token, the first entry further including a first set ofpermissions and the second entry further including a second set ofpermissions. The card services module issues one or more commands to thesecure element based on a first action requested by the first trustedapplication in conjunction with the presentation of the first digitaltoken only if the one or more commands will not violate the first set ofpermissions. The card services module issues one or more commands to thesecure element based on a second action requested by the second trustedapplication in conjunction with the presentation of the second digitaltoken only if the one or more commands will not violate the second setof permissions.

The present invention also relates to a method of providing first andsecond trusted applications diverse permission to communicate via asecure element associated with a portable communication device. A firstset of permissions is assigned to the first trusted application; asecond set of permissions is assigned to the second trusted application.The method also comprises requesting from the first trusted applicationthat a card services module operably associated with the secure elementimplement a first action; and issuing one or more commands to the secureelement based on the first action requested by the first trustedapplication only if the one or more commands will not violate the firstset of permissions.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the present disclosure, non-limiting andnon-exhaustive embodiments are described in reference to the followingdrawings. In the drawings, like reference numerals refer to like partsthrough all the various figures unless otherwise specified.

FIG. 1 a illustrates the diagnostic agent installed in the end user'sportable communication device asking whether she would like diagnosticsperformed following a failed attempt to use her device to conduct asecure payment transaction at a point of sale;

FIG. 1 b illustrates the operable interconnections between the enduser's smartphone and various subsystems, including the systemmanagement back end;

FIG. 2 is a block diagram illustrating some of the logical blocks withina portable communication device that may be relevant to the presentsystem;

FIG. 3 is a block diagram illustrating the logical blocks within thesystem management back end.

FIG. 4 is a block diagram illustrating further detail of the“OpenWallet” block of FIG. 2 that may be relevant to the present system.

FIGS. 4A, 4B, 4C and 4 d are illustrations of various screens from anexemplary wallet user interface 410 that may be deployed on a smartphone.

FIG. 5 is a block diagram illustrating the operable interconnectionsbetween the end user's smartphone, the control server, and the issuerserver.

FIG. 6 is a block diagram of one potential implementation of a systemunderlying the grant of permission for one of the third party apps 200to view, select and/or change secure data stored in the paymentsubsystem.

DETAILED DESCRIPTION

The present invention now will be described more fully hereinafter withreference to the accompanying drawings, which form a part hereof, andwhich show, by way of illustration, specific exemplary embodiments bywhich the invention may be practiced. This invention may, however, beembodied in many different forms and should not be construed as limitedto the embodiments set forth herein; rather, these embodiments areprovided so that this disclosure will be thorough and complete, and willfully convey the scope of the invention to those skilled in the art.Among other things, the present invention may be embodied as methods ordevices. Accordingly, the present invention may take the form of anentirely hardware embodiment, an entirely software embodiment or anembodiment combining software and hardware aspects. The followingdetailed description is, therefore, not to be taken in a limiting sense.

Portable Communication Devices

The present invention provides a system and method that can be utilizedwith a variety of different portable communication devices, includingbut not limited to PDA's, cellular phones, smart phones, laptops, tabletcomputers, and other mobile devices that include cellular voice and dataservice as well as preferable access to consumer downloadableapplications. One such portable communication device could be an iPhone,Motorola RAZR or DROID; however, the present invention is preferablyplatform and device independent. For example, the portable communicationdevice technology platform may be Microsoft Windows Mobile, MicrosoftWindows Phone 7, Palm OS, RIM Blackberry OS, Apple OS, Android OS,Symbian, Java or any other technology platform. For purposes of thisdisclosure, the present invention has been generally described inaccordance with features and interfaces that are optimized for a smartphone utilizing a generalized platform, although one skilled in the artwould understand that all such features and interfaces may also be usedand adapted for any other platform and/or device.

The portable communication device includes one or more short proximityelectromagnetic communication devices, such as an NFC, RFID, orBluetooth transceiver. It is presently preferred to use an NFC basebandthat is Compliant with NFC IP 1 standards (www.nfcforum.org), whichprovides standard functions like peer-to-peer data exchange,reader-writer mode (i.e. harvesting of information from RFID tags), andcontactless card emulation (per the NFC IP 1 and ISO 14443 standards)when paired with a secure element on the portable communication deviceand presented in front of a “contactless payment reader” (see below atpoint of sale). As would be understood in the art by those having thepresent specification, figures, and claims before them, the NFC IP 1standards are simply the presently preferred example, which could beexported—in whole or in part—for use in association with any otherproximity communication standard. It is further preferred that theportable communication device include an NFC/RFID antenna (conformed toNFC IP 1 and ISO 14443 standards) to enable near field communications.However, as would be understood in the art NFC/RFID communications maybe accomplished albeit over even shorter ranges and potential readproblems.

The portable communication device also includes a mobile networkinterface to establish and manage wireless communications with a mobilenetwork operator. The mobile network interface uses one or morecommunication protocols and technologies including, but not limited to,global system for mobile communication (GSM), 3G, 4G, code divisionmultiple access (CDMA), time division multiple access (TDMA), userdatagram protocol (UDP), transmission control protocol/Internet protocol(TCP/IP), SMS, general packet radio service (GPRS), WAP, ultra wide band(UWB), TFEE 802.16 Worldwide Interoperability for Microwave Access(WiMax), SIP/RTP, or any of a variety of other wireless communicationprotocols to communicate with the mobile network of a mobile networkoperator. Accordingly, the mobile network interface may include as atransceiver, transceiving device, or network interface card (NIC). It iscontemplated that the mobile network interface and short proximityelectromagnetic communication device could share a transceiver ortransceiving device, as would be understood in the art by those havingthe present specification, figures, and claims before them.

The portable communication device further includes a user interface thatprovides some means for the consumer to receive information as well asto input information or otherwise respond to the received information.As is presently understood (without intending to limit the presentdisclosure thereto) this user interface may include a microphone, anaudio speaker, a haptic interface, a graphical display, and a keypad,keyboard, pointing device and/or touch screen. As would be understood inthe art by those having the present specification, figures, and claimsbefore them, the portable communication device may further include alocation transceiver that can determine the physical coordinates ofdevice on the surface of the Earth typically as a function of itslatitude, longitude and altitude. This location transceiver preferablyuses GPS technology, so it may be referred to herein as a GPStransceiver; however, it should be understood that the locationtransceiver can additionally (or alternatively) employ othergeo-positioning mechanisms, including, but not limited to,triangulation, assisted GPS (AGPS), E-OTD, CI, SAI, ETA, BSS or thelike, to determine the physical location of the portable communicationdevice on the surface of the Earth.

The portable communication device will also include a microprocessor andmass memory. The mass memory may include ROM, RAM as well as one or moreremovable memory cards. The mass memory provides storage for computerreadable instructions and other data, including a basic input/outputsystem (“BIOS”) and an operating system for controlling the operation ofthe portable communication device. The portable communication devicewill also include a device identification memory dedicated to identifythe device, such as a SIM card. As is generally understood, SIM cardscontain the unique serial number of the device (ESN), an internationallyunique number of the mobile user (IMSI), security authentication andciphering information, temporary information related to the localnetwork, a list of the services the user has access to and two passwords(PIN for usual use and PUK for unlocking). As would be understood in theart by those having the present specification, figures, and claimsbefore them, other information may be maintained in the deviceidentification memory depending upon the type of device, its primarynetwork type, home mobile network operator, etc.

In the present invention each portable communication device is thoughtto have two subsystems: (1) a “wireless subsystem” that enablescommunication and other data applications as has become commonplace withusers of cellular telephones today, and (2) the “secure transactionalsubsystem” which may also be known as the “payment subsystem”. It iscontemplated that this secure transactional subsystem will preferablyinclude a Secure Element, similar (if not identical) to that describedas part of the Global Platform 2.1.X, 2.2, or 2.2.X(www.globalplatform.org). The secure element has been implemented as aspecialized, separate physical memory used for industry common practiceof storing payment card track data used with industry common point ofsale; additionally, other secure credentials that can be stored in thesecure element include employment badge credentials (enterprise accesscontrols), hotel and other card-based access systems and transitcredentials.

Mobile Network Operator

Each of the portable communications devices is connected to at least onemobile network operator. The mobile network operator generally providesphysical infrastructure that supports the wireless communicationservices, data applications and the secure transactional subsystem via aplurality of cell towers that communicate with a plurality of portablecommunication devices within each cell tower's associated cell. In turn,the cell towers may be in operable communication with the logicalnetwork of the mobile network operator, POTS, and the Internet to conveythe communications and data within the mobile network operator's ownlogical network as well as to external networks including those of othermobile network operators. The mobile network operators generally providesupport for one or more communication protocols and technologiesincluding, but not limited to, global system for mobile communication(GSM), 3G, 4G, code division multiple access (CDMA), time divisionmultiple access (TDMA), user datagram protocol (UDP), transmissioncontrol protocol/Internet protocol (TCP/IP), SMS, general packet radioservice (GPRS), WAP, ultra wide band (UWB), IEEE 802.16 WorldwideInteroperability for Microwave Access (WiMax), SIP/RTP, or any of avariety of other wireless communication protocols to communicate withthe portable communication devices.

Retail Subsystem

Standard at merchants today is an Internet Protocol connected paymentsystem that allows for transaction processing of debit, credit, prepayand gift products of banks and merchant service providers. By swiping amagnetic stripe enabled card at the magnetic reader of a Point of SaleTerminal, the card data is transferred to the point of sale equipmentand used to confirm funds by the issuing bank. This point of saleequipment has begun to include contactless card readers as accessoriesthat allow for the payment card data to be presented over an RFinterface, in lieu of the magnetic reader. The data is transferred tothe reader through the RF interface by the ISO 14443 standard andproprietary payment applications like PayPass and Paywave, whichtransmit the contactless card data from a card and in the future amobile device that includes a Payment Subsystem.

A retailer's point of sale device 75 may be connected to a network via awireless or wired connection. This point of sale network may include theInternet in addition to local area networks (LANs), wide area networks(WANs), direct connections, such as through a universal serial bus (USB)port, other forms of computer-readable media, or any combinationthereof. On an interconnected set of LANs, including those based ondiffering architectures and protocols, a router acts as a link betweenLANs, enabling messages to be sent from one to another. In addition,communication links within LANs typically include twisted wire pair orcoaxial cable, while communication links between networks may utilizeanalog telephone lines, full or fractional dedicated digital linesincluding T1, T2, T3, and T4, Integrated Services Digital Networks(ISDNs), Digital Subscriber Lines (DSLs), wireless links includingsatellite links, or other communications links known to those skilled inthe art. Furthermore, remote computers and other related electronicdevices could be remotely connected to either LANs or WANs via a modemand temporary telephone link. In essence, the point of sale network mayutilize any communication method that allows information to travelbetween the point of sale devices and financial services providers forthe purpose of validating, authorizing and ultimately capturingfinancial transactions at the point of sale for payment via the samefinancial service providers.

Secure Transactional Subsystem

The system includes a secure transactional subsystem. The securetransactional subsystem includes the secure element and associateddevice software for communication to management and provisioning systemsas well as the customer facing interface for use and management ofsecure data stored in the secure element. Preferably the securetransactional subsystem will conform, where appropriate, to aninternational standard, such as the standard defined in Global Platform2.1.X or 2.2.

System Management Back End

The system includes a system management back end. As shown in FIG. 1 b,the system management back end 300 is connected to the retail subsystem,the secure transactional subsystem and to a plurality of portablecommunication devices via the infrastructure of at least one mobilenetwork operator. The system management back end has a server operablycommunicating with one or more client devices. The server is also inoperable communication with the retailer subsystem, secure transactionalsubsystem, and one or more portable communication devices. The server isalso in operable communication with the retailer subsystem, securetransactional subsystem, and one or more portable communication devices.The communications include data and voice channels. Any type of voicechannel may be used in association with the present invention, includingbut not limited to VoIP.

The server may comprise one or more general-purpose computers thatimplement the procedures and functions needed to run the system backoffice in serial or in parallel on the same computer or across a localor wide area network distributed on a plurality of computers and mayeven be located “in the cloud” (preferably subject to the provision ofsufficient security). The computer(s) comprising the server may becontrolled by Linux, Windows®, Windows CE, Unix, or a Java® basedoperating system, to name a few. The system management back end serveris operably associated with mass memory that stores program code anddata. Data may include one or more databases, text, spreadsheet, folder,file, or the like, that may be configured to maintain and store aknowledge base, user identifiers (ESN, IMSI, PIN, telephone number,email/IM address, billing information, or the like).

The system management back end server supports a case management systemto provide call traffic connectivity and distribution across the clientcomputers in the customer care center. In a preferred approach usingVoIP voice channel connectivity, the case management system is acontact/case management system distributed by Contactual, Inc. ofRedwood City, Calif. The Contactual system is a standard CRM system fora VoIP-based customer care call center that also provides flexibility tohandle care issues with simultaneous payments and cellular-related careconcerns. As would be understood by one of ordinary skill in the arthaving the present specification, drawings and claims before them othercase management systems may be utilized within the present inventionsuch as Salesforce (Salesforce.com, inc. of San Francisco, Calif.) andNovo (Novo Solutions, Inc. of Virginia Beach, Va.).

Each client computer associated with the system management back endserver has a network interface device, graphical user interface, andvoice communication capabilities that match the voice channel(s)supported by the client care center server, such as VoIP. Each clientcomputer can request status of both the cellular and securetransactional subsystems of a portable communication device. This statusmay include the contents of the soft memory and core performance ofportable communication device, the NFC components: baseband, NFCantenna, secure element status and identification.

Federated Payment Subsystem

As shown in FIG. 2, each portable communication device 50 may containone or more third party applications 200 (e.g. selected by theconsumer), OpenWallet 100, payment libraries 110, secure element 120,NFC Baseband, a payment subsystem 150 (i.e. secure data store 115 andsecure element 120), and diagnostic agent 170. OpenWallet 100 is acomputer application that allows the consumer to see all credentials(e.g., card, coupon, access control and ticket data) stored in thedevice 50 (preferably in payment subsystem 150). OpenWallet 100 wouldalso preferably track the issuers of all the credentials stored in theportable communication device's payment subsystem 150 and determine onan application-by-application basis whether that third party applicationshould have permissions to view, select and/or change the credentialsstored in the payment subsystem. In this manner, OpenWallet 100 alsoprevents unauthorized applications from accessing data stored in thepayment subsystem 150, which they do not currently have permission toaccess.

The payment libraries 110 are used by OpenWallet 100 to manage (andperform housekeeping tasks on) the secure element 120, interface withthe system management back end, and perform over-the-air (OTA)provisioning via data communication transceiver (including its SMSchannel), on the device 50. It is contemplated that the OTA datacommunications will be encrypted in some manner and an encryption keywill be deployed in card service module 420. The payment subsystem 150may be used to store credentials such as payment card, coupon, accesscontrol and ticket data (e.g. transportation, concert). Some of thesepayment types may be added to the payment subsystem by differentapplications 200 for use by those applications. In this manner, otherthird party applications (not shown) may be precluded from accessing thepayment subsystem 150.

The secure data store 115 provides secured storage on the portablecommunication device 50. Various levels of security may be provideddepending upon the nature of the data intended for storage in securedata store 115. For instance, secure data store 115 may simply bepassword-protected at the operating system level of device 50. As isknown in these operating systems, the password may be a simplealphanumeric or hexadecimal code that is stored somewhere on the device50. Alternatively, the data in secure data store 115 is preferablyencrypted. More likely, however, the secure data store 115 will be setup as a virtual secure element in the manner disclosed in the co-pendingpatent application (owned by the assignee of the present application)entitled “System and Method for Providing A Virtual Secure Element on aPortable Communication Device” filed contemporaneously herewith andhereby incorporated by reference.

OpenWallet 100 preferably removes the complexity involved in thestorage, maintenance and use of credentials such as card, coupon,ticket, access control data from one or multiple sources or issuers inassociation with the payment subsystem 150. OpenWallet 100 alsopreferably enforces access control to the data stored in the paymentsubsystem 150 and the functions allowed by each application. In oneapproach, OpenWallet 100 verifies the author/issuer of each third partyapplication stored on the portable communication device 50. Thisverification may be accomplished by accessing a local authorizationdatabase of permitted (i.e., trusted) applications (see FIG. 6). Underthis approach, only applications that are signed with a known Issuer IDand the correctly associated Compile ID are allowed by card servicesmodule 420 to access and/or manipulate data stored in the paymentsubsystem 150 and/or meta data repository 125 (which stores, among otherthings, card image data and any embossed card data).

In other words, when an application 200 or wallet user interface 410needs to interact with the payment subsystem 150 it does so by passing adigital identifier (such as its Issuer ID or App ID), a digital token(i.e., Compile ID or Secret Token ID), the desired action, and anyassociated arguments needed for the action to the card services module420. Card services module 420 verifies the digital identifier-digitaltoken pair matches trusted application data in the secure data table(FIG. 6), and then would issue the one or more commands necessary toexecute the desired action. Among the potential actions that may be usedby applications 200 or wallet user interface 410 are those associatedwith:

-   -   a. wallet management (e.g. setting, resetting or enabling wallet        passcodes; get URL of OTA server; over-the-air registry        provisioning; setting payment timing; increasing payment timing;        set default card; list issuers, list supported credentials; set        display sequence of credentials; set credential storage        priority; create categories/folders; associate credentials with        categories; memory audit; determine SE for storage of        credential; get Offers; update wallet status)    -   b. credential management (e.g. add credential; view credential        detail; delete credential; activate credential (for        redemption/payment); deactivate credential; search credentials;        list credential capability; set default credential; lock/unlock        credential; require passcode access; get credential image; set        access passcode)    -   c. Secure Element (SE) Management (e.g. get credential; update        credential; update meta data; delete credential; wallet        lock/unlock; SE lock/unlock)    -   d. Personalization (e.g. add credential; delete credential;        suspend/unsuspend credential; notification for issuer metadata        update; notification for card metadata update)

FIG. 4 illustrates further detail of the “OpenWallet” block of FIG. 2.As shown, the functions of “OpenWallet” 100 can be integrated into asingle dedicated module that provides a user interface that is closelycoupled to the card services. In another embodiment illustrated in FIG.4, the capabilities and functionality of OpenWallet 100 may bedistributed between a Wallet User Interface 410 and a Card ServicesModule 420. The distributed approach would allow applications to havedirect access to the Card Services Module 420 without having to use theuser interface provided by Wallet User Interface 410. The Card ServicesModule 420 may be configured to track the issuer of all card, coupon,access and ticket data stored in the payment subsystem 150 of theportable communication device 50 and determine on anapplication-by-application basis whether an application should havepermissions to view, select, use and/or change secure data stored in thepayment subsystem. The wallet user interface 410 provides a userinterface through which a user may register, provision, access and/oruse the information securely stored in association with the cardservices module 420 relating to the user's credentials. Because thewallet user interface 410 is separated from the card services module420, the user may elect to use one of the third party applications 200to manage information in the Card Services Module 420. As further shownin FIG. 4, metadata (such as credential logos (e.g. Amtrak®,MasterCard®, TicketMaster®, and Visa®) and affinity images (e.g. AAAdvantage® and United Mileage Plus®)) may be stored in memory 125 foruse by the third party apps 200 or wallet user interface 410 inrendering a more friendly user experience. As this metadata can beshared across applications, the storage needed to implement securedtransaction may be minimized.

Various screen shots of one exemplary wallet user interface 410 that maybe deployed on a smart phone are shown in FIGS. 4A, 4B, 4C and 4D. Amongother things these figures illustrate the functionality of registering,provisioning, access and/or using information securely stored inassociation with the card services module 420. FIG. 4A depicts that thewallet can hold various credentials such as cards, coupons, tickets andmore. FIG. 4A further depicts that multiple cards may be stored in thewallet 100. As shown in FIG. 4D, upon selecting the VISA® card from thescreen illustrated in FIG. 4A, the wallet user interface opens anotherscreen that provides an interface for the user to initiate a secure NFCpayment transaction. As also depicted, the user interface may showbalance and available credit information.

Credential Provisioning

FIG. 5 illustrates one exemplary system architecture that may beutilized to provision credentials in the system. As shown, the user'sportable communication device 50 is configured to communicate with acontrol server and an issuer adapter. The control server (which mayalternatively be known as a Card Application Management System) isconfigured to validate a user's credentials. For example, if the userwishes to store information relating to a credit card in the secureelement 120 of their mobile device 50, they would input their creditcard information via a user interface displayed on their portable device50.

The user interface may be generated by wallet user interface 410 or atrusted third party application 200 supported by OpenWallet 100. As anexample, FIGS. 4A and 4B, illustrate the provisioning of a “Charge-ItCard” into the wallet using one exemplary wallet user interface 410 thatmay be deployed on a smart phone. Underlying either user interface, thecard services module 420 preferably transmits the first six digits ofthe identified credit card (commonly referred to as the BankIdentification Number or BIN) to the control server, which thenvalidates the card issuer's compliance rules and facilitates a directkey exchange between the OpenWallet 100 (or Card Services Module 420) onthe user's mobile device 50 and the appropriate issuer server in anencrypted fashion as was previously known in the art.

Various approaches to the direct key exchange may be facilitated by avariety of off-the-shelf solutions provided by entities including, butnot limited to, Gemalto N.V. (Amsterdam, The Netherlands), Giesecke &Devrient (Munich, Germany), SK C&C (Korea) (Corefire), or VIVOtech Inc.of Santa Clara, Calif. (ViVoTech Issuer Server). The Issuer Serverauthenticates the user, executes issuer rules and then initiate thepersonalization process. The Issuer Server is preferably a serveroperated by the issuer of the credentials that the user is seeking toprovision. The issuer server may verify the user, for example byproviding a series of verification questions based on user informationpreviously provided to the issuer (see FIG. 4B). Once verified, theissuer server passes the full 16 digit credit card number to the secureelement 120 via the card service module 420. The issuer server may alsopass metadata, such as information relating to the look and design ofthe selected credit card to the application memory 125. On completion,the issuer adapter would notify the control server about the completionof the transaction. As shown in FIG. 4C, following provisioning thewallet user interface 410 would include the Charge-It Card, which theuser could select using user interface techniques that are well-known inthe art of smart phone user interfaces.

Validating Third Party Applications

As noted above, OpenWallet 100 verifies the trusted status of any thirdparty application 200 before that application is allowed access to thesecure element 120 (or secure data store 115 and even preferably themeta data repository 125) on the portable communication device 50 toview, select and/or change secure data stored in the payment subsystem150. In one approach noted above, this verification may be accomplishedby accessing a local authorization database of permitted or trustedapplications. In a preferred approach, the local authorization databasein cooperates with a remote authorization database associated with oneor more servers associated with system management back end 300.

FIG. 6 is a block diagram of one potential implementation of onepotential combination local and remote authorization databases toenhance security of the card services module 420, secure element 120,and payment subsystem 150. As shown in FIG. 6, a User A/C Registry (orUser Account Registry) may be associated with the server (or otherwisedeployed in the cloud). The User A/C Registry may store theidentification of the secure element 120 disposed in each user'sportable device 50. Entries in the User Account Registry may be addedfor each user at any point in the process.

The “Issuer Registry” database is a database of approved Issuers. TheIssuer ID is unique for each type of credential. In other words, if abank has multiple types of credentials (e.g. debit cards, credit cards,affinity cards, etc.) each credential type would have its own Issuer ID(e.g. I-BofA-II). In a preferred approach, the Issuer ID as betweenmultiple types of credentials would have some common elements, so as toindicated that the credentials are at least related (e.g. I-BofA-I). Inthis way applications from same issuer can share data with the otherapplication of the same “extended” issuer. In a preferred approach, cardservices module 420 can be simplified by requiring even the wallet userinterface 410 (which “ships with the system”) to have an Issuer ID (andas well as an Application ID and Compile token).

The “Application Registry” is a database of applications (mostly thirdparty) that have pre-approved by an operating system provider. Like theUser A/C Registry, the “Application Registry” and “Issuer Registry”database are maintained on the server side (or otherwise in the cloud)in operable association with OpenIssuance (see FIG. 3). As would beunderstood by those of ordinary skill in the art having the presentspecification before them, the various registries may be implemented inseparate databases or one unified database. At initiation of a wallet100 and preferably at substantially regular time-intervals thereafter(e.g., daily), the data stored in the Application Registry of OpenIssuance (see, FIG. 3) is distributed to devices with the wallet to bestored locally.

As shown in FIG. 6, the Application Registry may include, among otherinformation, an Application ID (“App ID”), an Issuer ID, and a CompileID or token. The Compile ID is a global constant generated for eachapplication by one or more processes associated with Open Issuance (FIG.3) during the qualification process for the particular application 200.After it is generated by a particular card services module 420 on aunique device 50, the Compile token is included or otherwise associatedwith the application. This Compile token is preferably generated by apseudo-random number generator local to the device that uses apre-determined seed, such as the Application ID, Compile ID, Issuer IDor some combination thereof.

When the user seeks to qualify a third party application with the cardservices module 420 on a device 50, the Compile ID (a digital token) andApplication ID (a digital identifier) associated with the third partyapplication may be matched against the Compile ID and Application IDpairs stored in the Card Services Registry stored on the device 50 (seeFIG. 6). As should be understood by those skilled in the art having thepresent specification before them, the same Compile and Application IDpairs are transmitted to other devices 50 associated with the system, aswell. If the Compile ID/Application ID pair matches one of thepair-stored in the Card Services Registry on the device, a Secret TokenID is preferably generated on the device 50 by a pseudo-random numbergenerator (such as the one associated with the Secure Element 120 andthen stored in association with the Compile ID/Application ID pair inthe Card Services Registry on the device 50. In some instances, theCompile ID may be pre-selected and used to seed the random numbergenerator. It should be understood that one or more pieces of otherpredetermined data associated with the card services registry could bepreselected as the seed instead. The card services Registry ispreferably stored in secure memory (rather than the secure element 120because secure element 120 has limited real estate) and the CardServices Registry is preferably further encrypted using standardencryption techniques. The Secret Token ID is also embedded in orotherwise associated with the application 200 on the device 50 in placeof the Compile ID that was distributed with the application.

After the application has been loaded into the Card Services Registry(and the secret token embedded in the application), the third party maylaunch and may prompt the user to opt-in to provide access to theissuer-specific credential needed for the validated (or trusted)application. In each subsequent launch of the third party trustedapplication, the embedded Secret Token and/or Application ID arecompared to the data in the Card Services Registry on the device. Ifthere is match, the application is trusted and can access the paymentsubsystem 150 via card service module 420. In this manner, it can beseen that applications 200 or wallet user interface 410 may also beremoved from the Card Services Registry and thus would be disabled fromaccessing the payment subsystem and possibly the application,altogether.

Card services module 420 also preferably uses the trusted applicationverification step to determine the appropriate level of subsystem accessallowed for each application 200. For example, in one embodiment, oneapplication 200 a may be authorized to access and display all of thedata contained in the payment subsystem 150, where another third partyapplication 200× may be only authorized to access and display a subsetof the data contained in the payment subsystem 150. In yet anotherembodiment, an application may be permitted only to send a payment ortransaction requests to OpenWallet 100, but may not itself be permittedto access any of the data contained in the payment subsystem 150. In oneapproach, assignment of permissions to the application can be thought ofas follows:

Extended Issuer Own Reserved All Credentials Credentials CredentialsRead 0 0 or 1 0 or 1 0 or 1 Write 0 0 or 1 0 or 1 0 or 1 Delete 0 0 or 10 or 1 0 or 1 Activate/ 0 0 or 1 0 or 1 0 or 1 Deactivate Download 0 0or 1 0 or 1 0 or 1 CredentialThese permission can be used to form 4 hexadecimal number in the ordershown above from most to least significant figure. As shown in theexample Card Services Registry of FIG. 6, the I-BofA-II issuer haspermission level 11111, which can be thought to expand to 0001 0001 00010001 0001. In other words, the I-BofA-II application can read, write,delete, activate/deactivate, and download its own credentials but notthe extended issuer credentials let alone all credentials. If BofA hadanother issuer code (e.g. I-BofA-I), then that would be an extendedIssuer application. So, if the permission level of the applicationassociated with Issuer ID “I-BofA-II” was set to 0010 0001 0001 00100001 (or 21121 hexadecimal) then the application would be able to readand activate/deactivate the credentials associated with both issuer IDs.In yet another example, the wallet user interface 410 may be given apermission level of 44444 (i.e. 0100 0100 0100 0100 0100). In otherwords, the wallet user interface 410 can read, write, delete,activate/deactivate, and download all credentials. As would beunderstood by those of ordinary skill in the art, these are merelyexamples of potential permissions that can be granted to applications,other permissions are contemplated. For instance, some applications mayhave the ability to read extended issuer credentials, but only write,delete, activate and download the application's own credentials (e.g.21111, which expands to 0010 0001 0001 0001 0001). In yet anotherexample, an application may only be given activate/deactivate anddownload tights (e.g. 0000 0000 0000 0001 0001 or 00011 in hexadecimal).In yet another example, an application may be disabled—without beingdeleted from the trusted application database or Card ServiceRegistry—by setting all rights to zero.

The foregoing description and drawings merely explain and illustrate theinvention and the invention is not limited thereto. While thespecification is described in relation to certain implementation orembodiments, many details are set forth for the purpose of illustration.Thus, the foregoing merely illustrates the principles of the invention.For example, the invention may have other specific forms withoutdeparting from its spirit or essential characteristic. The describedarrangements are illustrative and not restrictive. To those skilled inthe art, the invention is susceptible to additional implementations orembodiments and certain of these details described in this applicationmay be varied considerably without departing from the basic principlesof the invention. It will thus be appreciated that those skilled in theart will be able to devise various arrangements which, although notexplicitly described or shown herein, embody the principles of theinvention and, thus, within its scope and spirit.

1. A system for providing first and second trusted applications diversepermission to communicate via a secure element associated with aportable communication device, the system comprising: a first digitalidentifier and a first digital token operably associated with the firsttrusted application; a second digital identifier and a second digitaltoken operably associated with the second trusted application; a cardservices module disposed on the portable communication device andoperably associated with the secure element to provide an applicationprogramming interface to the secure element; and a secure data tableelectronically associated with the card service module, the secure datatable including a first entry pairing the first digital identifier withthe first digital token and a second entry pairing the second digitalidentifier with the second digital token, the first entry furtherincluding a first set of permissions and the second entry furtherincluding a second set of permissions, wherein the card services moduleissues one or more commands to the secure element based on a firstaction requested by the first trusted application in conjunction withthe presentation of the first digital token only if the one or morecommands will not violate the first set of permissions and the cardservices module issues one or more commands to the secure element basedon a second action requested by the second trusted application inconjunction with the presentation of the second digital token only ifthe one more commands will not violate the second set of permissions. 2.The system according to claim 1 wherein the first and second sets ofpermissions are different.
 3. The system according to claim 2 whereinthe first and second sets of permissions govern reading, writing,activating/deactivating and downloading credentials.
 4. The systemaccording to claim 3 wherein the first and second set of permissionsapply independently to three categories: all credentials, owncredentials and extended issuer credentials.
 5. The system according toclaim 1 wherein the first and second sets of permissions govern reading,writing, activating/deactivating and downloading credentials.
 6. Thesystem according to claim 5 wherein the first and second set ofpermissions apply independently to three categories: all credentials,own credentials and extended issuer credentials.
 7. A method forproviding first and second trusted applications diverse permission tocommunicate via a secure element associated with a portablecommunication device, the method comprising: assigning a first set ofpermissions to the first trusted application; assigning a second set ofpermissions to the second trusted application; requesting from the firsttrusted application that a card services module operably associated withthe secure element implement a first action; and issuing one or morecommands to the secure element based on the first action requested bythe first trusted application only if the one or more commands will notviolate the first set of permissions.
 8. The method of claim 7 furthercomprising: requesting from the second trusted application that a cardservices module operably associated with the secure element implement asecond action; and issuing one or more commands to the secure elementbased on the second action requested by the second trusted applicationonly if the one or more commands will not violate the second set ofpermissions.
 9. The method according to claim 8 wherein the first andsecond sets of permissions are different.
 10. The method according toclaim 9 wherein the first and second sets of permissions govern reading,writing, activating/deactivating and downloading credentials.
 11. Themethod according to claim 10 wherein the first and second set ofpermissions apply independently to three categories: all credentials,own credentials and extended issuer credentials.
 12. The methodaccording to claim 7 wherein the first and second sets of permissionsgovern reading, writing, activating/deactivating and downloadingcredentials.
 13. The system according to claim 12 wherein the first andsecond set of permissions apply independently to three categories: allcredentials, own credentials and extended issuer credentials.